Conversation
|
Do you have another workflow run showing the original error? https://github.com/Kutsuja/Node-Podman-OpenShift-CI-CD isn't a public repo, so the run logs aren't available. Also, can you give an overview of the changes made to implement this feature? The formatting changes make it harder to spot the functional changes in the diffs. Thanks! |
| async getExistingImages(container: "docker" | "podman"): Promise<string[]> { | ||
| const existingSet = new Set<string>([]); | ||
| const ids = ( | ||
| await exec.exec(`${container} image ls -q`, [], { |
There was a problem hiding this comment.
What we see is that we have replaced docker image ls -q with ${container} image ls -q, in which we can specify ${container} to be either docker or podman.
|
Oh yeah sorry, I overlooked that. ChangelogWhat I did was to add an option to use either Error Logs
NoteworthyPossible bugWe can see the coverage test drop from 100% to 50% in OtherOld log with same
|
|
I've been testing podman locally and it doesn't appear to be fully compatible with the docker CLI:
The first two can be worked around, but if the last is correct then this action can't be updated to support podman. |
|
Ah, what a shame :{ |
Podman Support (Need help!)
Feature
Add optional parameter
containerthat takes indockerorpodman(defaults todocker).Issue
Podmannot using cache (even thoughCache restored successfully),I suspect might be caused by a different cache location.Refer to this read on Oracle.
Podman layer cache id isn't retrieved correctly.
Refer to this run.
Current Situation
Refer to this workflow run using this code.
TODO